feat: add npm publish workflow with trusted publishing#24
Merged
Conversation
sreya
commented
Nov 13, 2025
sreya
commented
Contributor
- Add automated publish workflow triggered by git tags (v*)
- Use OIDC trusted publishing (no NPM_TOKEN needed)
- Add tag validation to prevent version mismatches
- Update package name to 'ghostty-web' (unscoped)
- Remove incorrect repository.directory field
- Generate provenance attestation for all published packages
- Add automated publish workflow triggered by git tags (v*) - Use OIDC trusted publishing (no NPM_TOKEN needed) - Add tag validation to prevent version mismatches - Update package name to 'ghostty-web' (unscoped) - Remove incorrect repository.directory field - Generate provenance attestation for all published packages
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.